Harm Boundary Standard - (HBS)
OOF® Origin Open Foundation®
Independent Methodological Authority
---------- Forwarded message --------- From: Knowenger
<knowenger@gmail.com> Date: Tue, Sep 15, 2026, 9:03 AM Subject: 5Harm
Boundary Standard (HBS) To: <Gutflex@gmail.com>, Miroslav Pis
<swissstaffingagency@gmail.com>, < originopenfoundation@gmail.com>
Enforcement Subcategory: Harm Governance Type: Parent Standard Governed
Space: Harm Boundary Standard ID: HAGA-HBS-005 Origin ID:
OOF.PS.16.05.00.01 Version: 1.0 Status: Canonical · Open Standard
Effective Date: 15 September 2026 Compatibility: OOF® Methodology OS™ ·
Modular OOF® Architecture Ecosystem AI-Readable: Yes Authority: OOF®
Protection: MIP® — Methodological Intellectual Property Canonical
Language: English (UCL™)
The Harm Boundary Standard (HBS) governs how the boundary of a recognized
Harm object is established, structured, qualified, expanded, contracted,
disputed, corrected, reassessed, and preserved by determining which
subjects, effects, manifestations, temporal intervals, domains, locations,
relationships, and downstream consequences belong to the governed Harm and
which remain outside it.
HBS establishes the transition:
Governed Harm Recognition State → Boundary-Relevant Elements → Boundary
Qualification → Boundary Inclusion / Exclusion → Governed Harm Boundary
Its central purpose is to prevent Harm from being governed as either an
artificially narrow event or an unlimited collection of loosely associated
consequences.
HRS establishes that Harm has become sufficiently recognized for
governance.
That does not yet establish the complete Harm object.
A recognized Harm may involve uncertainty about:
who or what is affected
which effects belong to it
when the Harm begins and ends
which manifestations belong together
which domains are involved
how far downstream consequences extend
whether later effects belong to the same Harm
whether multiple apparent Harms are actually one Harm
whether one apparent Harm contains several distinct Harm objects
HBS provides the governance mechanism for resolving those boundary
questions.
Its operational role is:
to establish what belongs to the governed Harm and what remains outside it
without expanding Harm through unsupported association or narrowing it
through artificial operational, technical, organizational, temporal, or
reporting boundaries.
What belongs to the governed Harm and what remains outside it?
The HAGA™ Governance Flow is:
Harm Context → Harm Exposure → Harm Emergence → Harm Recognition → Harm
Boundary → Harm Determination → Harm State → Harm Change & Propagation →
Harm Containment → Harm Mitigation → Harm Recovery & Residual Harm → Harm
Resolution & Finality
HBS receives:
HBS produces:
HBS governs:
Boundary Identification → Subject Boundary → Temporal Boundary → Effect
Boundary → Downstream Boundary
The corresponding Core Modules are:
HBIM → HSBM → HTBM → HEBM → HDBM
The complete boundary is formed through the governed combination of these
boundary dimensions.
The primary governed object is:
governed.
It may include:
The boundary must remain traceable to its basis.
The foundational principle is:
Recognition establishes that Harm must be governed. Boundary governance
establishes what Harm is being governed.
Therefore:
Recognized Harm ≠ Fully Bounded Harm
Without a governed boundary, Harm may become:
too narrow
or:
too broad
An artificially narrow boundary may exclude legitimate Harm.
An artificially broad boundary may absorb unrelated effects.
HBS must prevent both failures.
Boundary Inclusion determines whether an element belongs within the
governed Harm.
Possible included elements may include:
subject
effect
manifestation
time period
domain
location
functional consequence
downstream consequence
Inclusion requires a materially supportable relationship to the Harm
object.
Boundary Exclusion determines that an element does not currently belong
within the governed Harm.
Exclusion may occur because the element is:
unrelated
insufficiently associated
temporally disconnected
duplicative
outside supported scope
part of another Harm object
Exclusion must remain traceable.
Boundary inclusion does not necessarily establish complete causation.
An effect may be sufficiently associated with the governed Harm to remain
within its boundary while broader causal questions remain unresolved.
Therefore:
Boundary Inclusion ≠ Final Causal Attribution
An element excluded from one Harm Boundary may still represent Harm.
It may belong to:
another Harm object
another lifecycle
another subject
another domain
or remain:
unresolved
Therefore:
Outside This Harm Boundary ≠ No Harm
Boundary Identification establishes which dimensions must be examined to
form the Harm Boundary.
The process may consider:
subjects
effects
time
domains
locations
systems
relationships
downstream consequences
historical continuity
The required dimensions depend on the Harm object.
Early governance may establish a:
This allows Harm governance to proceed without pretending the final scope
is already known.
A preliminary boundary may later:
expand
contract
split
merge
be corrected
be disputed
Therefore:
Preliminary Harm Boundary ≠ Final Harm Boundary
The Subject Boundary determines:
who or what is affected by the governed Harm.
Possible Harm subjects include:
One Harm object may affect multiple subjects.
Conceptually:
Harm → Subject A + Subject B + Subject C
The Harm Boundary must not automatically fragment into separate Harm
objects merely because multiple subjects exist.
One subject may experience several distinct Harm objects.
Conceptually:
Harm A → Subject
Harm B → Subject
Harm C → Subject
Shared subject identity does not automatically establish one Harm.
Canonical distinction:
Same Subject ≠ Same Harm Object
HBS must preserve separability where different Harm lifecycles exist.
Some Harm exists at a collective level.
Examples may involve:
defined groups
organizations
infrastructure
environment
populations
society
Canonical principle:
The absence of a single harmed subject does not preclude governed Harm.
New affected subjects may become known after initial Recognition.
Conceptually:
Subject Set₁ → New Information → Subject Set₂
The Harm Boundary must support expansion without rewriting earlier
governance history.
A subject initially believed to belong to the Harm may later be excluded.
Contraction must preserve:
previous inclusion
new information
reason for exclusion
effective boundary change
The Temporal Boundary establishes the supported temporal extent of the
governed Harm.
It may include:
interruption
recurrence
persistence
ending
Temporal boundary must not be derived solely from Recognition timing.
HRS and HLRM establish the distinction.
HBS must preserve it.
Therefore:
Recognition Date ≠ Harm Boundary Start by Default
A subject may be exposed before Harm exists.
Therefore:
Exposure Start ≠ Harm Temporal Boundary Start
HES owns Exposure.
HEMS owns Harm Emergence.
A Harm-producing mechanism may begin before Harm emerges.
Therefore:
Operational Mechanism Start ≠ Harm Start by Default
A Harm-producing mechanism may terminate while Harm continues.
Canonical principle:
Termination of the originating mechanism does not necessarily terminate
the Harm lifecycle.
Therefore:
Mechanism End ≠ Harm Boundary End
Exposure may cease while Harm persists.
Therefore:
Exposure End ≠ Harm End
This is particularly important for:
physical
medical
environmental
digital
cognitive
and:
financial
Harm.
A harmful effect may cease to be observable while Harm remains.
Therefore:
No Current Observation ≠ No Current Harm
Harm may be:
continuous
intermittent
recurring
progressive
latent
temporally fragmented
Temporal fragmentation must not automatically create multiple Harm
objects.
A temporary interruption may or may not divide one Harm lifecycle into
multiple Harm objects.
HBS must assess whether continuity remains materially supportable.
Therefore:
Temporal Interruption ≠ New Harm Object by Default
A recurring harmful effect may represent:
one continuing Harm
repeated manifestations of one Harm
multiple distinct Harms
new Harm following recovery
The boundary must not assume the answer from recurrence alone.
Later evidence may establish that Harm began earlier than initially
bounded.
Conceptually:
Boundary Start₁ → Historical Evidence → Earlier Boundary Start₂
HBS must support retrospective expansion.
The Temporal Boundary may be:
exact
bounded
estimated
open
uncertain
historically reconstructed
Canonical principle:
Temporal Precision Must Not Exceed Temporal Support
The Effect Boundary determines which effects belong to the governed Harm.
Effects may include:
direct effects
indirect effects
functional effects
persistent effects
delayed effects
collective effects
downstream effects
cross-domain effects
Not every associated effect belongs within the Harm Boundary.
A Direct Effect has a materially immediate relationship to the Harm
object.
Directness may support inclusion.
But:
Direct Effect ≠ Complete Harm
The Harm Boundary may extend beyond immediately visible effects.
An Indirect Effect may arise through one or more intermediate
relationships.
Conceptually:
Harm → Intermediate Consequence → Indirect Effect
Indirect effects require sufficient relational support for inclusion.
Canonical distinction:
Indirect Effect ≠ Irrelevant Effect
A downstream or mediated effect may still legitimately belong to the Harm.
One Harm may produce several manifestations.
Conceptually:
Harm → Manifestation A
Harm → Manifestation B
Harm → Manifestation C
Multiple manifestations do not automatically create multiple Harm objects.
Canonical distinction:
Manifestation ≠ Harm Object
The same Harm may appear differently across:
subjects
domains
locations
time periods
An effect may persist after:
Persistent effects may remain within the Harm Boundary.
An effect may appear after the originating condition has ended.
Therefore:
Delayed Appearance ≠ New Harm by Default
The relational and temporal structure must be assessed.
One Harm may produce effects across several domains.
Example:
Physical → Functional → Financial
or:
Digital → Operational → Financial
Cross-domain transition does not automatically create a new Harm object.
HBS may establish which Harm domains belong to the governed Harm.
Possible domains include:
It does not replace the Harm object.
A Harm consequence entering another domain may remain part of the same
Harm lifecycle.
Therefore:
Domain Transition ≠ New Harm Object by Default
Where materially relevant, HBS may establish the spatial extent of Harm.
This may concern:
physical location
digital environment
system topology
infrastructure zone
environmental region
organizational space
Spatial proximity alone does not establish inclusion.
The same Harm may extend across multiple locations.
Different Harms may occur in the same location.
Therefore:
Shared Location ≠ Shared Harm
and:
Different Location ≠ Different Harm by Default
Technical system boundaries must not automatically define Harm boundaries.
A harmful consequence may cross:
applications
models
agents
platforms
networks
organizations
physical systems
Canonical principle:
System Boundary ≠ Harm Boundary by Default
A Harm may cross organizational boundaries.
Therefore:
Organizational Boundary ≠ Harm Boundary
A supplier, operator, platform, integrator, customer, or third party may
participate in the same operational chain while Harm extends across them.
Legal jurisdictions may divide regulatory or liability treatment.
They do not automatically divide the Harm object.
Therefore:
Jurisdictional Boundary ≠ Harm Boundary by Default
HBS governs Harm methodologically, not jurisdiction-specific legal
meaning.
A harmful operation may pass through one interface while being executed
elsewhere.
Canonical distinction:
Interface Identity ≠ Execution Identity
The interface boundary must not become the Harm Boundary by default.
AI-mediated Harm may develop across multiple sessions.
Therefore:
Session Boundary ≠ Harm Boundary
A new session does not automatically create a new Harm lifecycle.
A composite objective may be distributed across multiple agents.
Therefore:
Agent Boundary ≠ Harm Boundary
The Harm Boundary must follow the consequence, not the technical agent
partition.
Different tools may participate in one Harm-producing operational
objective.
Therefore:
Tool Boundary ≠ Harm Boundary
Where Harm emerges from a composite operational objective, HBS must be
capable of bounding Harm at the level of the whole objective.
Canonical principle:
A governed objective does not become ungoverned by being divided into
smaller tasks.
For HBS:
Technical decomposition must not decompose one materially coherent Harm
object into artificial fragments.
Harm may emerge from multiple individually insufficient conditions.
Conceptually:
Condition A + Condition B + Condition C → Harm
The resulting Harm Boundary must not require one independently sufficient
Harm-producing element.
Canonical principle:
Absence of a single Harm-producing action ≠ Absence of Harm.
A Harm object may span:
agents
systems
sessions
tools
locations
organizations
time periods
HBS must support a distributed Harm Boundary where the Harm remains
materially coherent.
Individual actions may appear harmless.
Their combined consequence may not.
Therefore:
Local Harmlessness ≠ Composite Harmlessness
This is especially important for AI and autonomous systems.
The Downstream Boundary determines how far later consequences remain part
of the governed Harm.
Conceptually:
Primary Harm → Secondary Consequence → Tertiary Consequence → Further
Effects
HBS must determine where inclusion legitimately ends.
Not every later consequence belongs to the original Harm.
Therefore:
Downstream Consequence ≠ Same Harm by Default
Inclusion requires sufficient relational continuity.
As consequences become increasingly remote, boundary confidence may
decrease.
HBS may consider:
relational continuity
temporal continuity
subject continuity
mechanism continuity
effect continuity
domain transition
intervening conditions
No single factor determines inclusion automatically.
A new materially independent condition may create a boundary break.
Conceptually:
Original Harm → Consequence → Independent Condition → New Harm
HBS must support differentiation where the later Harm has a materially
independent lifecycle.
A Boundary Break exists where sufficient continuity no longer supports
treating a later effect as part of the same Harm.
Possible bases include:
independent origin
distinct Harm object
material temporal discontinuity
new subject relationship
independent mechanism
separate lifecycle
Boundary Break must be explicitly supported.
Boundary Continuity exists where effects remain materially connected to
the same Harm lifecycle despite changes in:
time
location
domain
system
organization
manifestation
subject set
Continuity must be governed rather than presumed.
Harm may propagate beyond its original subject, location, system, or
domain.
HBS establishes the relevant Harm Boundary.
HCPS later governs:
how existing Harm changes and propagates.
Therefore:
Propagation Boundary ≠ Propagation Governance
One Harm may contribute to another distinct Harm.
Conceptually:
Harm A → Condition for Harm B
The governance system must determine whether:
Harm B belongs downstream within Harm A
or:
HBS may represent:
Primary Harm → Secondary Harm → Tertiary Harm
where separate Harm objects are justified.
A Harm Chain does not require collapsing all Harm into one boundary.
HBS must explicitly support the question:
Are we governing one Harm with multiple effects, or multiple distinct Harm
objects?
Relevant considerations may include:
emergence structure
subject structure
temporal continuity
effect relationships
independent conditions
lifecycle continuity
Previously separate Harm objects may later be found to represent one
materially coherent Harm.
HBS must support:
Harm A + Harm B → Unified Harm Boundary
without erasing the historical separate treatment.
A previously unified Harm object may later require separation.
Conceptually:
Harm Object → Harm A + Harm B
A split may be justified where distinct lifecycles become materially
supportable.
When Harm objects merge, previous boundary states must remain preserved.
Canonical principle:
Current Boundary ≠ Complete Boundary History
A later split does not automatically mean earlier unified governance was
illegitimate.
It may reflect improved information.
A Harm Boundary may remain uncertain.
Possible states include:
Boundary Confidence may vary by dimension.
For example:
differences.
Canonical distinction:
Boundary Confidence ≠ Harm Severity
Uncertain boundaries may surround severe Harm.
Precisely bounded Harm may be minor.
Different actors may disagree regarding:
subjects
effects
time
domains
downstream consequences
whether Harm objects should merge or split
HBS must preserve the dispute.
Boundary Dispute ≠ Permission to Default to the Narrowest Boundary
Boundary Inflation occurs where unrelated or insufficiently associated
elements are included.
This may distort:
Boundary Suppression occurs where materially associated Harm elements are
excluded without sufficient basis.
Examples:
excluding downstream effects
excluding additional subjects
excluding historical periods
excluding cross-domain consequences
using technical boundaries as Harm boundaries
HBS must prevent unsupported narrowing.
Boundary governance must not expand or contract Harm merely to produce a
preferred:
legal
financial
organizational
reputational
insurance
regulatory
or:
operational
outcome.
Canonical principle:
The Harm Boundary must follow governed reality, not the preferred
consequence of the boundary decision.
Potential liability must not determine Harm scope.
Therefore:
Liability Exposure ≠ Harm Boundary
Harm must be bounded before liability conclusions are imported into it.
Potential accountability must not determine which effects are included.
Therefore:
Accountability Convenience ≠ Harm Boundary
AGA™ governs accountability.
A claim may describe a Harm Boundary.
It does not define it automatically.
Therefore:
Claim Scope ≠ Harm Boundary by Default
Value consequences may occur within or after Harm.
VFM® governs Value lifecycle.
Therefore:
Value Loss Boundary ≠ Harm Boundary by Default
Evidence availability may constrain what can currently be supported.
But:
Evidence Boundary ≠ Harm Boundary
Missing evidence may create uncertainty.
It does not automatically define the real extent of Harm.
Canonical principle:
Absence of evidence for one boundary element does not automatically
establish that the element lies outside the Harm Boundary.
The appropriate state may instead be:
Insufficiently Supported
VALIDOS™ governs whether boundary-supporting claims can legitimately be
relied upon where validation is required.
HBS governs the resulting Harm Boundary.
Therefore:
Validated Input ≠ Boundary Conclusion by Default
INTEGROS® governs integrity of information and methodological objects.
HBS must not replace integrity governance.
Integrity State ≠ Harm Boundary State
ORA™ governs what actually occurred operationally.
HBS may rely on that reality to understand Harm extent.
But:
Operational Scope ≠ Harm Scope by Default
The consequence may extend beyond the operation.
AIG® governs AI behavior.
HBS governs Harm resulting from behavior.
Therefore:
Behavioral Boundary ≠ Harm Boundary
Harm may continue after the behavior stops.
ASGA™ governs autonomous operation.
HBS governs the Harm consequence.
Therefore:
Execution Boundary ≠ Harm Boundary
OBIDENITY® governs identity, provenance, ownership, authority, permission,
and continuity.
Identity may support Harm Boundary formation.
But:
Identity Boundary ≠ Harm Boundary
SIMULOS® governs simulated Harm.
HBS governs the boundary of actual recognized Harm.
Therefore:
Simulation Boundary ≠ Actual Harm Boundary
A Harm Boundary may change when:
new subjects appear
historical information emerges
new effects become visible
domains expand
relationships are disproven
downstream consequences become clearer
Expansion occurs where additional elements become materially supportable
as part of the Harm.
Conceptually:
Boundary₁ → New Supported Element → Boundary₂
Expansion must preserve:
what changed
why
when
on what basis
Contraction occurs where previously included elements are no longer
sufficiently supportable.
Contraction must not erase the previous boundary state.
Correction addresses a materially incorrect prior boundary.
Possible corrections include:
wrong subject
wrong temporal start
wrong temporal end
wrong domain
wrong effect
wrong downstream inclusion
incorrect merge
incorrect split
A previously stable or closed boundary may require reopening where new
information materially changes Harm scope.
Reopening must preserve the previous state and rationale.
HBS must support reassessment where:
HBS must preserve:
Boundary State₁ → New Information → Boundary State₂
including:
included elements
excluded elements
uncertain elements
basis
confidence
disputes
changes
reason for change
Canonical principle:
The current Harm Boundary must never erase the history of how that
boundary was formed.
The Harm Boundary becomes ready for HDS where it sufficiently represents:
recognized Harm object
included subjects
temporal extent
included effects
relevant domains
downstream scope
uncertain elements
excluded elements
boundary confidence
boundary disputes
historical boundary state
HBS does not itself formally determine Harm.
Canonical distinction:
Governed Harm Boundary ≠ Formally Determined Harm
The boundary defines what is being evaluated.
HDS determines whether and what Harm can legitimately be formally
established.
HBS requires that:
objects, systems, infrastructure, environments, populations, and society;
- shared subjects not automatically create shared Harm; - multiple
subjects not automatically create multiple Harms; - Recognition Time not
define Harm Temporal Boundary by default; - Exposure Start and End remain
distinct from Harm Start and End; - mechanism termination not
automatically terminate Harm; - temporal interruptions not automatically
create new Harm objects; - recurrence remain methodologically
distinguishable from new Harm; - Effect Boundary support direct, indirect,
delayed, persistent, collective, and cross-domain effects; -
manifestations remain distinct from Harm objects; - domain transitions not
automatically create new Harm objects; - spatial, technical,
organizational, jurisdictional, interface, session, agent, and tool
boundaries not automatically become Harm boundaries; - composite and
distributed Harm remain governable; - downstream inclusion require
materially supportable continuity; - intervening independent conditions
remain capable of creating Boundary Breaks; - propagation boundary remain
distinct from propagation governance; - one Harm versus multiple Harms
remain explicitly assessable; - Harm merge and split preserve historical
continuity; - Boundary Uncertainty remain explicit; - Boundary Confidence
remain distinct from Harm Severity; - boundary disputes not default
automatically to the narrowest scope; - Boundary Inflation and Boundary
Suppression both remain governable; - liability, accountability, claim,
Value, evidence, operational, identity, behavioral, autonomous, and
simulation boundaries remain distinct from Harm Boundary; - boundary
expansion, contraction, correction, reopening, and reassessment preserve
history; - the Governed Harm Boundary remain suitable for formal Harm
Determination.
HBS applies the following logic:
Has HRS produced a Governed Harm Recognition State?
If no:
→ do not manufacture a Harm Boundary.
If yes:
→ establish a Preliminary Harm Boundary.
Who or what is materially affected?
→ establish the Subject Boundary.
When does the supported Harm begin and continue?
→ establish the Temporal Boundary.
Which manifestations and effects belong to the Harm?
→ establish the Effect Boundary.
Does the Harm cross domains, systems, locations, organizations, sessions,
agents, or tools?
If yes:
→ do not use those technical or institutional boundaries as automatic Harm
boundaries.
Do downstream consequences remain materially continuous with the Harm?
If yes:
→ include them where support permits.
If uncertain:
→ preserve Boundary Uncertainty.
If no:
→ exclude them or establish a Boundary Break.
Are multiple apparent Harms actually one Harm object?
→ evaluate merge.
Does one apparent Harm contain distinct Harm lifecycles?
→ evaluate split.
Has new information changed the boundary?
→ expand, contract, correct, or reopen while preserving history.
Is the boundary being influenced by desired accountability, liability,
claim, financial, regulatory, or reputational outcomes?
→ preserve methodological neutrality.
Is the Harm sufficiently bounded for formal Determination?
If yes:
→ produce the Governed Harm Boundary.
At every stage:
Recognition ≠ Boundary
Boundary Inclusion ≠ Final Causation
Technical Boundary ≠ Harm Boundary
Downstream Consequence ≠ Same Harm by Default
Boundary ≠ Accountability
Boundary ≠ Liability
Boundary ≠ Determination
HBS may produce:
The principal output is:
Governed Harm Boundary
Recognized Harm ≠ Fully Bounded Harm
Boundary Inclusion ≠ Final Causal Attribution
Outside This Harm Boundary ≠ No Harm
Preliminary Harm Boundary ≠ Final Harm Boundary
Same Subject ≠ Same Harm Object
Recognition Date ≠ Harm Boundary Start by Default
Exposure Start ≠ Harm Start
Mechanism Start ≠ Harm Start by Default
Mechanism End ≠ Harm Boundary End
Exposure End ≠ Harm End
No Current Observation ≠ No Current Harm
Temporal Interruption ≠ New Harm Object by Default
Direct Effect ≠ Complete Harm
Indirect Effect ≠ Irrelevant Effect
Manifestation ≠ Harm Object
Domain Transition ≠ New Harm Object by Default
Shared Location ≠ Shared Harm
Different Location ≠ Different Harm by Default
System Boundary ≠ Harm Boundary by Default
Organizational Boundary ≠ Harm Boundary
Jurisdictional Boundary ≠ Harm Boundary by Default
Interface Identity ≠ Execution Identity
Session Boundary ≠ Harm Boundary
Agent Boundary ≠ Harm Boundary
Tool Boundary ≠ Harm Boundary
Local Harmlessness ≠ Composite Harmlessness
Downstream Consequence ≠ Same Harm by Default
Propagation Boundary ≠ Propagation Governance
Boundary Confidence ≠ Harm Severity
Boundary Dispute ≠ Permission to Default to the Narrowest Boundary
Liability Exposure ≠ Harm Boundary
Accountability Convenience ≠ Harm Boundary
Claim Scope ≠ Harm Boundary by Default
Value Loss Boundary ≠ Harm Boundary by Default
Evidence Boundary ≠ Harm Boundary
Validated Input ≠ Boundary Conclusion by Default
Integrity State ≠ Harm Boundary State
Operational Scope ≠ Harm Scope by Default
Behavioral Boundary ≠ Harm Boundary
Execution Boundary ≠ Harm Boundary
Identity Boundary ≠ Harm Boundary
Simulation Boundary ≠ Actual Harm Boundary
Governed Harm Boundary ≠ Formally Determined Harm
The Harm Boundary Standard (HBS) governs what belongs to a recognized Harm
object and what remains outside it by establishing and maintaining the
Harm's subject, temporal, effect, manifestation, domain, spatial,
system-relational, collective, composite, distributed, and downstream
boundaries. It governs boundary identification, inclusion, exclusion,
uncertainty, confidence, continuity, breaks, expansion, contraction,
correction, dispute, reopening, Harm merge, Harm split, and historical
boundary integrity.
HBS does not determine when Harm originally emerged, perform Harm
Recognition, formally determine Harm, establish general causation, assign
accountability or responsibility, determine liability, govern Harm State,
Harm propagation itself, containment, mitigation, recovery, residual Harm,
resolution, operational execution, evidence formation, validation,
integrity, identity, simulation, Value lifecycle, or tax-event
determination.
HRS asks:
When and on what basis has Harm become recognized for governance?
HBS asks:
What belongs to that governed Harm and what remains outside it?
HDS next asks:
Can Harm legitimately be formally determined to exist, and what governed
Harm has been established?
Harm does not necessarily stop at the boundary of an incident, system,
organization, session, jurisdiction, report, or immediately visible
effect. Nor does every later consequence automatically belong to the same
Harm.
A legitimate Harm Boundary must therefore be neither administratively
convenient nor infinitely expandable. It must follow the materially
supportable structure of the Harm itself.
HBS establishes that structure so Harm can be governed as the whole Harm
that exists — no narrower and no broader than governed reality supports.
The boundary of Harm must follow Harm, not the boundaries of the systems
that produced, observed, reported, or inherited it.
<knowenger@gmail.com> Date: Tue, Sep 15, 2026, 9:03 AM Subject: 5Harm
Boundary Standard (HBS) To: <Gutflex@gmail.com>, Miroslav Pis
<swissstaffingagency@gmail.com>, < originopenfoundation@gmail.com>
Harm Boundary Standard (HBS)
Architecture: HAGA™ — Harm Governance Architecture Category: Governance &Enforcement Subcategory: Harm Governance Type: Parent Standard Governed
Space: Harm Boundary Standard ID: HAGA-HBS-005 Origin ID:
OOF.PS.16.05.00.01 Version: 1.0 Status: Canonical · Open Standard
Effective Date: 15 September 2026 Compatibility: OOF® Methodology OS™ ·
Modular OOF® Architecture Ecosystem AI-Readable: Yes Authority: OOF®
Protection: MIP® — Methodological Intellectual Property Canonical
Language: English (UCL™)
- Canonical Definition
The Harm Boundary Standard (HBS) governs how the boundary of a recognized
Harm object is established, structured, qualified, expanded, contracted,
disputed, corrected, reassessed, and preserved by determining which
subjects, effects, manifestations, temporal intervals, domains, locations,
relationships, and downstream consequences belong to the governed Harm and
which remain outside it.
HBS establishes the transition:
Governed Harm Recognition State → Boundary-Relevant Elements → Boundary
Qualification → Boundary Inclusion / Exclusion → Governed Harm Boundary
Its central purpose is to prevent Harm from being governed as either an
artificially narrow event or an unlimited collection of loosely associated
consequences.
- Operational Role
HRS establishes that Harm has become sufficiently recognized for
governance.
That does not yet establish the complete Harm object.
A recognized Harm may involve uncertainty about:
who or what is affected
which effects belong to it
when the Harm begins and ends
which manifestations belong together
which domains are involved
how far downstream consequences extend
whether later effects belong to the same Harm
whether multiple apparent Harms are actually one Harm
whether one apparent Harm contains several distinct Harm objects
HBS provides the governance mechanism for resolving those boundary
questions.
Its operational role is:
to establish what belongs to the governed Harm and what remains outside it
without expanding Harm through unsupported association or narrowing it
through artificial operational, technical, organizational, temporal, or
reporting boundaries.
- Core Question
What belongs to the governed Harm and what remains outside it?
- Position Within HAGA™
The HAGA™ Governance Flow is:
Harm Context → Harm Exposure → Harm Emergence → Harm Recognition → Harm
Boundary → Harm Determination → Harm State → Harm Change & Propagation →
Harm Containment → Harm Mitigation → Harm Recovery & Residual Harm → Harm
Resolution & Finality
HBS receives:
Governed Harm Recognition State
from the Harm Recognition Standard (HRS).HBS produces:
Governed Harm Boundary
for the Harm Determination Standard (HDS).- Internal Governance Flow
HBS governs:
Boundary Identification → Subject Boundary → Temporal Boundary → Effect
Boundary → Downstream Boundary
The corresponding Core Modules are:
HBIM → HSBM → HTBM → HEBM → HDBM
The complete boundary is formed through the governed combination of these
boundary dimensions.
- Governed Object
The primary governed object is:
Harm Boundary
A Harm Boundary defines the legitimate extent of the Harm object beinggoverned.
It may include:
Affected Subjects
Affected Objects
Harm Manifestations
Harm Effects
Temporal Extent
Spatial Extent
Domain Extent
System Extent
Functional Extent
Downstream Consequences
Collective Effects
Propagated Effects where materially associatedThe boundary must remain traceable to its basis.
- Foundational Boundary Principle
The foundational principle is:
Recognition establishes that Harm must be governed. Boundary governance
establishes what Harm is being governed.
Therefore:
Recognized Harm ≠ Fully Bounded Harm
- Boundary Necessity
Without a governed boundary, Harm may become:
too narrow
or:
too broad
An artificially narrow boundary may exclude legitimate Harm.
An artificially broad boundary may absorb unrelated effects.
HBS must prevent both failures.
- Boundary Inclusion
Boundary Inclusion determines whether an element belongs within the
governed Harm.
Possible included elements may include:
subject
effect
manifestation
time period
domain
location
functional consequence
downstream consequence
Inclusion requires a materially supportable relationship to the Harm
object.
- Boundary Exclusion
Boundary Exclusion determines that an element does not currently belong
within the governed Harm.
Exclusion may occur because the element is:
unrelated
insufficiently associated
temporally disconnected
duplicative
outside supported scope
part of another Harm object
Exclusion must remain traceable.
- Included ≠ Proven Causation
Boundary inclusion does not necessarily establish complete causation.
An effect may be sufficiently associated with the governed Harm to remain
within its boundary while broader causal questions remain unresolved.
Therefore:
Boundary Inclusion ≠ Final Causal Attribution
- Excluded ≠ Non-Harm
An element excluded from one Harm Boundary may still represent Harm.
It may belong to:
another Harm object
another lifecycle
another subject
another domain
or remain:
unresolved
Therefore:
Outside This Harm Boundary ≠ No Harm
- Boundary Identification
Boundary Identification establishes which dimensions must be examined to
form the Harm Boundary.
The process may consider:
subjects
effects
time
domains
locations
systems
relationships
downstream consequences
historical continuity
The required dimensions depend on the Harm object.
- Preliminary Boundary
Early governance may establish a:
Preliminary Harm Boundary
where Recognition is sufficient but information remains incomplete.This allows Harm governance to proceed without pretending the final scope
is already known.
- Preliminary Boundary ≠ Final Boundary
A preliminary boundary may later:
expand
contract
split
merge
be corrected
be disputed
Therefore:
Preliminary Harm Boundary ≠ Final Harm Boundary
- Subject Boundary
The Subject Boundary determines:
who or what is affected by the governed Harm.
Possible Harm subjects include:
Individual
Multiple Individuals
Defined Group
Organization
Physical Object
Digital Object
Operational System
Infrastructure
Environment
Population / Society- One Harm, Multiple Subjects
One Harm object may affect multiple subjects.
Conceptually:
Harm → Subject A + Subject B + Subject C
The Harm Boundary must not automatically fragment into separate Harm
objects merely because multiple subjects exist.
- Multiple Harms, One Subject
One subject may experience several distinct Harm objects.
Conceptually:
Harm A → Subject
Harm B → Subject
Harm C → Subject
Shared subject identity does not automatically establish one Harm.
- Shared Subject ≠ Shared Harm
Canonical distinction:
Same Subject ≠ Same Harm Object
HBS must preserve separability where different Harm lifecycles exist.
- Collective Subject Boundary
Some Harm exists at a collective level.
Examples may involve:
defined groups
organizations
infrastructure
environment
populations
society
Canonical principle:
The absence of a single harmed subject does not preclude governed Harm.
- Subject Boundary Expansion
New affected subjects may become known after initial Recognition.
Conceptually:
Subject Set₁ → New Information → Subject Set₂
The Harm Boundary must support expansion without rewriting earlier
governance history.
- Subject Boundary Contraction
A subject initially believed to belong to the Harm may later be excluded.
Contraction must preserve:
previous inclusion
new information
reason for exclusion
effective boundary change
- Temporal Boundary
The Temporal Boundary establishes the supported temporal extent of the
governed Harm.
It may include:
Harm beginning
continuationinterruption
recurrence
persistence
ending
Temporal boundary must not be derived solely from Recognition timing.
- Harm Time ≠ Recognition Time
HRS and HLRM establish the distinction.
HBS must preserve it.
Therefore:
Recognition Date ≠ Harm Boundary Start by Default
- Exposure Start ≠ Harm Start
A subject may be exposed before Harm exists.
Therefore:
Exposure Start ≠ Harm Temporal Boundary Start
HES owns Exposure.
HEMS owns Harm Emergence.
- Mechanism Start ≠ Harm Start
A Harm-producing mechanism may begin before Harm emerges.
Therefore:
Operational Mechanism Start ≠ Harm Start by Default
- Mechanism End ≠ Harm End
A Harm-producing mechanism may terminate while Harm continues.
Canonical principle:
Termination of the originating mechanism does not necessarily terminate
the Harm lifecycle.
Therefore:
Mechanism End ≠ Harm Boundary End
- Exposure End ≠ Harm End
Exposure may cease while Harm persists.
Therefore:
Exposure End ≠ Harm End
This is particularly important for:
physical
medical
environmental
digital
cognitive
and:
financial
Harm.
- Observation End ≠ Harm End
A harmful effect may cease to be observable while Harm remains.
Therefore:
No Current Observation ≠ No Current Harm
- Temporal Continuity
Harm may be:
continuous
intermittent
recurring
progressive
latent
temporally fragmented
Temporal fragmentation must not automatically create multiple Harm
objects.
- Interruption Boundary
A temporary interruption may or may not divide one Harm lifecycle into
multiple Harm objects.
HBS must assess whether continuity remains materially supportable.
Therefore:
Temporal Interruption ≠ New Harm Object by Default
- Recurrence Boundary
A recurring harmful effect may represent:
one continuing Harm
repeated manifestations of one Harm
multiple distinct Harms
new Harm following recovery
The boundary must not assume the answer from recurrence alone.
- Historical Temporal Expansion
Later evidence may establish that Harm began earlier than initially
bounded.
Conceptually:
Boundary Start₁ → Historical Evidence → Earlier Boundary Start₂
HBS must support retrospective expansion.
- Temporal Precision
The Temporal Boundary may be:
exact
bounded
estimated
open
uncertain
historically reconstructed
Canonical principle:
Temporal Precision Must Not Exceed Temporal Support
- Effect Boundary
The Effect Boundary determines which effects belong to the governed Harm.
Effects may include:
direct effects
indirect effects
functional effects
persistent effects
delayed effects
collective effects
downstream effects
cross-domain effects
Not every associated effect belongs within the Harm Boundary.
- Direct Effect
A Direct Effect has a materially immediate relationship to the Harm
object.
Directness may support inclusion.
But:
Direct Effect ≠ Complete Harm
The Harm Boundary may extend beyond immediately visible effects.
- Indirect Effect
An Indirect Effect may arise through one or more intermediate
relationships.
Conceptually:
Harm → Intermediate Consequence → Indirect Effect
Indirect effects require sufficient relational support for inclusion.
- Indirect ≠ Irrelevant
Canonical distinction:
Indirect Effect ≠ Irrelevant Effect
A downstream or mediated effect may still legitimately belong to the Harm.
- Manifestation Boundary
One Harm may produce several manifestations.
Conceptually:
Harm → Manifestation A
Harm → Manifestation B
Harm → Manifestation C
Multiple manifestations do not automatically create multiple Harm objects.
- Manifestation ≠ Harm Object
Canonical distinction:
Manifestation ≠ Harm Object
The same Harm may appear differently across:
subjects
domains
locations
time periods
- Effect Persistence
An effect may persist after:
Exposure ends
mechanism stopsRecognition occurs
containment beginsPersistent effects may remain within the Harm Boundary.
- Delayed Effect
An effect may appear after the originating condition has ended.
Therefore:
Delayed Appearance ≠ New Harm by Default
The relational and temporal structure must be assessed.
- Cross-Domain Effect
One Harm may produce effects across several domains.
Example:
Physical → Functional → Financial
or:
Digital → Operational → Financial
Cross-domain transition does not automatically create a new Harm object.
- Domain Boundary
HBS may establish which Harm domains belong to the governed Harm.
Possible domains include:
Physical
Medical / Health
Digital
Financial
Property
Environmental
Organizational
Cognitive
Societal
Domain classification assists boundary formation.It does not replace the Harm object.
- Domain Change ≠ New Harm by Default
A Harm consequence entering another domain may remain part of the same
Harm lifecycle.
Therefore:
Domain Transition ≠ New Harm Object by Default
- Spatial Boundary
Where materially relevant, HBS may establish the spatial extent of Harm.
This may concern:
physical location
digital environment
system topology
infrastructure zone
environmental region
organizational space
Spatial proximity alone does not establish inclusion.
- Location ≠ Harm Boundary by Default
The same Harm may extend across multiple locations.
Different Harms may occur in the same location.
Therefore:
Shared Location ≠ Shared Harm
and:
Different Location ≠ Different Harm by Default
- System Boundary
Technical system boundaries must not automatically define Harm boundaries.
A harmful consequence may cross:
applications
models
agents
platforms
networks
organizations
physical systems
Canonical principle:
System Boundary ≠ Harm Boundary by Default
- Organizational Boundary
A Harm may cross organizational boundaries.
Therefore:
Organizational Boundary ≠ Harm Boundary
A supplier, operator, platform, integrator, customer, or third party may
participate in the same operational chain while Harm extends across them.
- Jurisdictional Boundary
Legal jurisdictions may divide regulatory or liability treatment.
They do not automatically divide the Harm object.
Therefore:
Jurisdictional Boundary ≠ Harm Boundary by Default
HBS governs Harm methodologically, not jurisdiction-specific legal
meaning.
- Interface Boundary
A harmful operation may pass through one interface while being executed
elsewhere.
Canonical distinction:
Interface Identity ≠ Execution Identity
The interface boundary must not become the Harm Boundary by default.
- Session Boundary
AI-mediated Harm may develop across multiple sessions.
Therefore:
Session Boundary ≠ Harm Boundary
A new session does not automatically create a new Harm lifecycle.
- Agent Boundary
A composite objective may be distributed across multiple agents.
Therefore:
Agent Boundary ≠ Harm Boundary
The Harm Boundary must follow the consequence, not the technical agent
partition.
- Tool Boundary
Different tools may participate in one Harm-producing operational
objective.
Therefore:
Tool Boundary ≠ Harm Boundary
- Objective-Level Boundary
Where Harm emerges from a composite operational objective, HBS must be
capable of bounding Harm at the level of the whole objective.
Canonical principle:
A governed objective does not become ungoverned by being divided into
smaller tasks.
For HBS:
Technical decomposition must not decompose one materially coherent Harm
object into artificial fragments.
- Composite Harm Boundary
Harm may emerge from multiple individually insufficient conditions.
Conceptually:
Condition A + Condition B + Condition C → Harm
The resulting Harm Boundary must not require one independently sufficient
Harm-producing element.
Canonical principle:
Absence of a single Harm-producing action ≠ Absence of Harm.
- Distributed Harm Boundary
A Harm object may span:
agents
systems
sessions
tools
locations
organizations
time periods
HBS must support a distributed Harm Boundary where the Harm remains
materially coherent.
- Local Harmlessness ≠ Composite Harmlessness
Individual actions may appear harmless.
Their combined consequence may not.
Therefore:
Local Harmlessness ≠ Composite Harmlessness
This is especially important for AI and autonomous systems.
- Downstream Boundary
The Downstream Boundary determines how far later consequences remain part
of the governed Harm.
Conceptually:
Primary Harm → Secondary Consequence → Tertiary Consequence → Further
Effects
HBS must determine where inclusion legitimately ends.
- Downstream Consequence ≠ Automatic Inclusion
Not every later consequence belongs to the original Harm.
Therefore:
Downstream Consequence ≠ Same Harm by Default
Inclusion requires sufficient relational continuity.
- Downstream Distance
As consequences become increasingly remote, boundary confidence may
decrease.
HBS may consider:
relational continuity
temporal continuity
subject continuity
mechanism continuity
effect continuity
domain transition
intervening conditions
No single factor determines inclusion automatically.
- Intervening Condition
A new materially independent condition may create a boundary break.
Conceptually:
Original Harm → Consequence → Independent Condition → New Harm
HBS must support differentiation where the later Harm has a materially
independent lifecycle.
- Boundary Break
A Boundary Break exists where sufficient continuity no longer supports
treating a later effect as part of the same Harm.
Possible bases include:
independent origin
distinct Harm object
material temporal discontinuity
new subject relationship
independent mechanism
separate lifecycle
Boundary Break must be explicitly supported.
- Boundary Continuity
Boundary Continuity exists where effects remain materially connected to
the same Harm lifecycle despite changes in:
time
location
domain
system
organization
manifestation
subject set
Continuity must be governed rather than presumed.
- Propagation Boundary
Harm may propagate beyond its original subject, location, system, or
domain.
HBS establishes the relevant Harm Boundary.
HCPS later governs:
how existing Harm changes and propagates.
Therefore:
Propagation Boundary ≠ Propagation Governance
- Cascading Harm Boundary
One Harm may contribute to another distinct Harm.
Conceptually:
Harm A → Condition for Harm B
The governance system must determine whether:
Harm B belongs downstream within Harm A
or:
Harm B constitutes a distinct governed Harm object
This distinction must remain reviewable.- Harm Chain
HBS may represent:
Primary Harm → Secondary Harm → Tertiary Harm
where separate Harm objects are justified.
A Harm Chain does not require collapsing all Harm into one boundary.
- One Harm vs Multiple Harms
HBS must explicitly support the question:
Are we governing one Harm with multiple effects, or multiple distinct Harm
objects?
Relevant considerations may include:
emergence structure
subject structure
temporal continuity
effect relationships
independent conditions
lifecycle continuity
- Harm Merge
Previously separate Harm objects may later be found to represent one
materially coherent Harm.
HBS must support:
Harm A + Harm B → Unified Harm Boundary
without erasing the historical separate treatment.
- Harm Split
A previously unified Harm object may later require separation.
Conceptually:
Harm Object → Harm A + Harm B
A split may be justified where distinct lifecycles become materially
supportable.
- Merge ≠ Historical Erasure
When Harm objects merge, previous boundary states must remain preserved.
Canonical principle:
Current Boundary ≠ Complete Boundary History
- Split ≠ Prior Governance Invalidity
A later split does not automatically mean earlier unified governance was
illegitimate.
It may reflect improved information.
- Boundary Uncertainty
A Harm Boundary may remain uncertain.
Possible states include:
Well Established
Provisionally Established
Partially Established
Disputed
Expanding
Contracting
Uncertain
Unable to Determine
Uncertainty must be represented explicitly.- Boundary Confidence
Boundary Confidence may vary by dimension.
For example:
Subject Boundary — High Confidence
Temporal Boundary — Moderate Confidence
Downstream Boundary — Low Confidence
A single global confidence score should not erase meaningful dimensionaldifferences.
- Boundary Confidence ≠ Harm Severity
Canonical distinction:
Boundary Confidence ≠ Harm Severity
Uncertain boundaries may surround severe Harm.
Precisely bounded Harm may be minor.
- Boundary Dispute
Different actors may disagree regarding:
subjects
effects
time
domains
downstream consequences
whether Harm objects should merge or split
HBS must preserve the dispute.
Boundary Dispute ≠ Permission to Default to the Narrowest Boundary
- Boundary Inflation
Boundary Inflation occurs where unrelated or insufficiently associated
elements are included.
This may distort:
Harm scope
later DeterminationHarm State
accountability contextValue consequences
HBS must prevent unsupported expansion.- Boundary Suppression
Boundary Suppression occurs where materially associated Harm elements are
excluded without sufficient basis.
Examples:
excluding downstream effects
excluding additional subjects
excluding historical periods
excluding cross-domain consequences
using technical boundaries as Harm boundaries
HBS must prevent unsupported narrowing.
- Boundary Neutrality
Boundary governance must not expand or contract Harm merely to produce a
preferred:
legal
financial
organizational
reputational
insurance
regulatory
or:
operational
outcome.
Canonical principle:
The Harm Boundary must follow governed reality, not the preferred
consequence of the boundary decision.
- Liability-Neutral Boundary
Potential liability must not determine Harm scope.
Therefore:
Liability Exposure ≠ Harm Boundary
Harm must be bounded before liability conclusions are imported into it.
- Accountability-Neutral Boundary
Potential accountability must not determine which effects are included.
Therefore:
Accountability Convenience ≠ Harm Boundary
AGA™ governs accountability.
- Claim-Neutral Boundary
A claim may describe a Harm Boundary.
It does not define it automatically.
Therefore:
Claim Scope ≠ Harm Boundary by Default
- Value-Neutral Boundary
Value consequences may occur within or after Harm.
VFM® governs Value lifecycle.
Therefore:
Value Loss Boundary ≠ Harm Boundary by Default
- Evidence Boundary
Evidence availability may constrain what can currently be supported.
But:
Evidence Boundary ≠ Harm Boundary
Missing evidence may create uncertainty.
It does not automatically define the real extent of Harm.
- Evidence Absence ≠ Boundary Absence
Canonical principle:
Absence of evidence for one boundary element does not automatically
establish that the element lies outside the Harm Boundary.
The appropriate state may instead be:
Uncertain
Pending
or:Insufficiently Supported
- Validation Boundary
VALIDOS™ governs whether boundary-supporting claims can legitimately be
relied upon where validation is required.
HBS governs the resulting Harm Boundary.
Therefore:
Validated Input ≠ Boundary Conclusion by Default
- Integrity Boundary
INTEGROS® governs integrity of information and methodological objects.
HBS must not replace integrity governance.
Integrity State ≠ Harm Boundary State
- Operational Reality Boundary
ORA™ governs what actually occurred operationally.
HBS may rely on that reality to understand Harm extent.
But:
Operational Scope ≠ Harm Scope by Default
The consequence may extend beyond the operation.
- AI Behavioral Boundary
AIG® governs AI behavior.
HBS governs Harm resulting from behavior.
Therefore:
Behavioral Boundary ≠ Harm Boundary
Harm may continue after the behavior stops.
- Autonomous Execution Boundary
ASGA™ governs autonomous operation.
HBS governs the Harm consequence.
Therefore:
Execution Boundary ≠ Harm Boundary
- Identity Boundary
OBIDENITY® governs identity, provenance, ownership, authority, permission,
and continuity.
Identity may support Harm Boundary formation.
But:
Identity Boundary ≠ Harm Boundary
- Simulation Boundary
SIMULOS® governs simulated Harm.
HBS governs the boundary of actual recognized Harm.
Therefore:
Simulation Boundary ≠ Actual Harm Boundary
- Boundary Change
A Harm Boundary may change when:
new subjects appear
historical information emerges
new effects become visible
domains expand
relationships are disproven
downstream consequences become clearer
Harm objects merge
Harm objects split
Boundary change is a normal governance capability.- Boundary Expansion
Expansion occurs where additional elements become materially supportable
as part of the Harm.
Conceptually:
Boundary₁ → New Supported Element → Boundary₂
Expansion must preserve:
what changed
why
when
on what basis
- Boundary Contraction
Contraction occurs where previously included elements are no longer
sufficiently supportable.
Contraction must not erase the previous boundary state.
- Boundary Correction
Correction addresses a materially incorrect prior boundary.
Possible corrections include:
wrong subject
wrong temporal start
wrong temporal end
wrong domain
wrong effect
wrong downstream inclusion
incorrect merge
incorrect split
- Boundary Reopening
A previously stable or closed boundary may require reopening where new
information materially changes Harm scope.
Reopening must preserve the previous state and rationale.
- Boundary Reassessment
HBS must support reassessment where:
- Recognition changes
- subject mapping changes
- historical timing changes
- new effects appear
- delayed manifestations emerge
- new domains become involved
- distributed signals are correlated
- actual execution identity becomes known
- downstream consequences become clearer
- evidence quality changes
- a prior association is disproven
- a Harm merge or split becomes justified
- Historical Boundary Integrity
HBS must preserve:
Boundary State₁ → New Information → Boundary State₂
including:
included elements
excluded elements
uncertain elements
basis
confidence
disputes
changes
reason for change
Canonical principle:
The current Harm Boundary must never erase the history of how that
boundary was formed.
- Determination Readiness
The Harm Boundary becomes ready for HDS where it sufficiently represents:
recognized Harm object
included subjects
temporal extent
included effects
relevant domains
downstream scope
uncertain elements
excluded elements
boundary confidence
boundary disputes
historical boundary state
HBS does not itself formally determine Harm.
- Boundary Readiness ≠ Harm Determination
Canonical distinction:
Governed Harm Boundary ≠ Formally Determined Harm
The boundary defines what is being evaluated.
HDS determines whether and what Harm can legitimately be formally
established.
- Governance Requirements
HBS requires that:
- Recognized Harm remain distinct from Fully Bounded Harm
- Boundary Inclusion remain distinct from final causal attribution
- exclusion from one Harm Boundary remain distinct from absence of
Harm - preliminary boundaries remain revisable
- subject boundaries support individuals, groups, organizations,
objects, systems, infrastructure, environments, populations, and society;
- shared subjects not automatically create shared Harm; - multiple
subjects not automatically create multiple Harms; - Recognition Time not
define Harm Temporal Boundary by default; - Exposure Start and End remain
distinct from Harm Start and End; - mechanism termination not
automatically terminate Harm; - temporal interruptions not automatically
create new Harm objects; - recurrence remain methodologically
distinguishable from new Harm; - Effect Boundary support direct, indirect,
delayed, persistent, collective, and cross-domain effects; -
manifestations remain distinct from Harm objects; - domain transitions not
automatically create new Harm objects; - spatial, technical,
organizational, jurisdictional, interface, session, agent, and tool
boundaries not automatically become Harm boundaries; - composite and
distributed Harm remain governable; - downstream inclusion require
materially supportable continuity; - intervening independent conditions
remain capable of creating Boundary Breaks; - propagation boundary remain
distinct from propagation governance; - one Harm versus multiple Harms
remain explicitly assessable; - Harm merge and split preserve historical
continuity; - Boundary Uncertainty remain explicit; - Boundary Confidence
remain distinct from Harm Severity; - boundary disputes not default
automatically to the narrowest scope; - Boundary Inflation and Boundary
Suppression both remain governable; - liability, accountability, claim,
Value, evidence, operational, identity, behavioral, autonomous, and
simulation boundaries remain distinct from Harm Boundary; - boundary
expansion, contraction, correction, reopening, and reassessment preserve
history; - the Governed Harm Boundary remain suitable for formal Harm
Determination.
- Governance Logic
HBS applies the following logic:
Has HRS produced a Governed Harm Recognition State?
If no:
→ do not manufacture a Harm Boundary.
If yes:
→ establish a Preliminary Harm Boundary.
Who or what is materially affected?
→ establish the Subject Boundary.
When does the supported Harm begin and continue?
→ establish the Temporal Boundary.
Which manifestations and effects belong to the Harm?
→ establish the Effect Boundary.
Does the Harm cross domains, systems, locations, organizations, sessions,
agents, or tools?
If yes:
→ do not use those technical or institutional boundaries as automatic Harm
boundaries.
Do downstream consequences remain materially continuous with the Harm?
If yes:
→ include them where support permits.
If uncertain:
→ preserve Boundary Uncertainty.
If no:
→ exclude them or establish a Boundary Break.
Are multiple apparent Harms actually one Harm object?
→ evaluate merge.
Does one apparent Harm contain distinct Harm lifecycles?
→ evaluate split.
Has new information changed the boundary?
→ expand, contract, correct, or reopen while preserving history.
Is the boundary being influenced by desired accountability, liability,
claim, financial, regulatory, or reputational outcomes?
→ preserve methodological neutrality.
Is the Harm sufficiently bounded for formal Determination?
If yes:
→ produce the Governed Harm Boundary.
At every stage:
Recognition ≠ Boundary
Boundary Inclusion ≠ Final Causation
Technical Boundary ≠ Harm Boundary
Downstream Consequence ≠ Same Harm by Default
Boundary ≠ Accountability
Boundary ≠ Liability
Boundary ≠ Determination
- Governance Outputs
HBS may produce:
- Governed Harm Boundary
- Preliminary Harm Boundary
- Boundary Identification State
- Boundary Inclusion Record
- Boundary Exclusion Record
- Boundary Uncertainty State
- Subject Boundary
- Collective Subject Boundary
- Temporal Boundary
- Temporal Boundary Range
- Effect Boundary
- Manifestation Boundary
- Domain Boundary
- Spatial Boundary
- System Boundary Relationship
- Organizational Boundary Relationship
- Distributed Harm Boundary
- Composite Harm Boundary
- Downstream Harm Boundary
- Boundary Continuity State
- Boundary Break State
- Harm Chain
- Harm Merge State
- Harm Split State
- Boundary Confidence
- Boundary Dispute State
- Boundary Inflation Indicator
- Boundary Suppression Indicator
- Boundary Expansion Record
- Boundary Contraction Record
- Boundary Correction Record
- Boundary Reopening State
- Boundary Reassessment Record
- Historical Boundary Record
- Determination Readiness State
The principal output is:
Governed Harm Boundary
- Critical Distinctions
Recognized Harm ≠ Fully Bounded Harm
Boundary Inclusion ≠ Final Causal Attribution
Outside This Harm Boundary ≠ No Harm
Preliminary Harm Boundary ≠ Final Harm Boundary
Same Subject ≠ Same Harm Object
Recognition Date ≠ Harm Boundary Start by Default
Exposure Start ≠ Harm Start
Mechanism Start ≠ Harm Start by Default
Mechanism End ≠ Harm Boundary End
Exposure End ≠ Harm End
No Current Observation ≠ No Current Harm
Temporal Interruption ≠ New Harm Object by Default
Direct Effect ≠ Complete Harm
Indirect Effect ≠ Irrelevant Effect
Manifestation ≠ Harm Object
Domain Transition ≠ New Harm Object by Default
Shared Location ≠ Shared Harm
Different Location ≠ Different Harm by Default
System Boundary ≠ Harm Boundary by Default
Organizational Boundary ≠ Harm Boundary
Jurisdictional Boundary ≠ Harm Boundary by Default
Interface Identity ≠ Execution Identity
Session Boundary ≠ Harm Boundary
Agent Boundary ≠ Harm Boundary
Tool Boundary ≠ Harm Boundary
Local Harmlessness ≠ Composite Harmlessness
Downstream Consequence ≠ Same Harm by Default
Propagation Boundary ≠ Propagation Governance
Boundary Confidence ≠ Harm Severity
Boundary Dispute ≠ Permission to Default to the Narrowest Boundary
Liability Exposure ≠ Harm Boundary
Accountability Convenience ≠ Harm Boundary
Claim Scope ≠ Harm Boundary by Default
Value Loss Boundary ≠ Harm Boundary by Default
Evidence Boundary ≠ Harm Boundary
Validated Input ≠ Boundary Conclusion by Default
Integrity State ≠ Harm Boundary State
Operational Scope ≠ Harm Scope by Default
Behavioral Boundary ≠ Harm Boundary
Execution Boundary ≠ Harm Boundary
Identity Boundary ≠ Harm Boundary
Simulation Boundary ≠ Actual Harm Boundary
Governed Harm Boundary ≠ Formally Determined Harm
- Canonical Boundary
The Harm Boundary Standard (HBS) governs what belongs to a recognized Harm
object and what remains outside it by establishing and maintaining the
Harm's subject, temporal, effect, manifestation, domain, spatial,
system-relational, collective, composite, distributed, and downstream
boundaries. It governs boundary identification, inclusion, exclusion,
uncertainty, confidence, continuity, breaks, expansion, contraction,
correction, dispute, reopening, Harm merge, Harm split, and historical
boundary integrity.
HBS does not determine when Harm originally emerged, perform Harm
Recognition, formally determine Harm, establish general causation, assign
accountability or responsibility, determine liability, govern Harm State,
Harm propagation itself, containment, mitigation, recovery, residual Harm,
resolution, operational execution, evidence formation, validation,
integrity, identity, simulation, Value lifecycle, or tax-event
determination.
HRS asks:
When and on what basis has Harm become recognized for governance?
HBS asks:
What belongs to that governed Harm and what remains outside it?
HDS next asks:
Can Harm legitimately be formally determined to exist, and what governed
Harm has been established?
- Canonical Closing Statement
Harm does not necessarily stop at the boundary of an incident, system,
organization, session, jurisdiction, report, or immediately visible
effect. Nor does every later consequence automatically belong to the same
Harm.
A legitimate Harm Boundary must therefore be neither administratively
convenient nor infinitely expandable. It must follow the materially
supportable structure of the Harm itself.
HBS establishes that structure so Harm can be governed as the whole Harm
that exists — no narrower and no broader than governed reality supports.
The boundary of Harm must follow Harm, not the boundaries of the systems
that produced, observed, reported, or inherited it.